Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4841dd2142cb644308d17903e9dd7b24a8e2b3a85e289ed1d434eeb8782ef536

Tx prefix hash: 14d5e3d57e90dbaf5d8fa6d581c430b14ccda76b0423862283b3ef39eb0c2fd9
Tx public key: 7e2b77a742f57276d9af0bf615abc39e79e0e4dde45bf52c645ec3bdfe112463
Timestamp: 1581091072 Timestamp [UCT]: 2020-02-07 15:57:52 Age [y:d:h:m:s]: 05:036:23:45:15
Block: 60702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1178519 RingCT/type: yes/0
Extra: 017e2b77a742f57276d9af0bf615abc39e79e0e4dde45bf52c645ec3bdfe11246302110000000312c4732d000000000000000000

1 output(s) for total of 386.251245366000 dcy

stealth address amount amount idx
00: a36e8434193c41931ee37e1a2e72b6536c78077b57c816a69246ad6ebb43c903 386.251245366000 111750 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": 60712, "vin": [ { "gen": { "height": 60702 } } ], "vout": [ { "amount": 386251245366, "target": { "key": "a36e8434193c41931ee37e1a2e72b6536c78077b57c816a69246ad6ebb43c903" } } ], "extra": [ 1, 126, 43, 119, 167, 66, 245, 114, 118, 217, 175, 11, 246, 21, 171, 195, 158, 121, 224, 228, 221, 228, 91, 245, 44, 100, 94, 195, 189, 254, 17, 36, 99, 2, 17, 0, 0, 0, 3, 18, 196, 115, 45, 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