Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 64df6f3068ef9b5de737a53a87b4f96f9befa66a9c4ba8d2a8c7f14ad3670906

Tx prefix hash: f067d821510292877c4280dbcd018510ccf712cc8b28971cbd60b0fab3bde565
Tx public key: e835781fa1bc2031a9f14d8db81138c102eaa0a6956a2a989d27abb62f9d7bfe
Timestamp: 1582902480 Timestamp [UCT]: 2020-02-28 15:08:00 Age [y:d:h:m:s]: 05:224:20:52:45
Block: 73502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1312641 RingCT/type: yes/0
Extra: 01e835781fa1bc2031a9f14d8db81138c102eaa0a6956a2a989d27abb62f9d7bfe02110000000b4943cd9f000000000000000000

1 output(s) for total of 350.314538394000 dcy

stealth address amount amount idx
00: 1e77a2644f7ca836bb0df08b2be65f9bd51190aef656439848ce4c536950e19f 350.314538394000 135605 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 73512, "vin": [ { "gen": { "height": 73502 } } ], "vout": [ { "amount": 350314538394, "target": { "key": "1e77a2644f7ca836bb0df08b2be65f9bd51190aef656439848ce4c536950e19f" } } ], "extra": [ 1, 232, 53, 120, 31, 161, 188, 32, 49, 169, 241, 77, 141, 184, 17, 56, 193, 2, 234, 160, 166, 149, 106, 42, 152, 157, 39, 171, 182, 47, 157, 123, 254, 2, 17, 0, 0, 0, 11, 73, 67, 205, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8