Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80c3da40106a06feb278f774503ad2975715d4ef7227d00b27bf89ee93e72aed

Tx prefix hash: 21e7a8a77f62f97a180aaed0beaddb65a6cac6779e5d74cc51a0c3677925d690
Tx public key: 78709c4e6b4f7971ec718d2fee16c8405446c0efe974f4dfd4e97d8af85401aa
Timestamp: 1628027818 Timestamp [UCT]: 2021-08-03 21:56:58 Age [y:d:h:m:s]: 03:183:06:55:32
Block: 306789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 903472 RingCT/type: yes/0
Extra: 0178709c4e6b4f7971ec718d2fee16c8405446c0efe974f4dfd4e97d8af85401aa02110000001f58045e5b000000000000000000

1 output(s) for total of 59.085534605000 dcy

stealth address amount amount idx
00: b8211b3018dd0e23161e946137a2191e1b0e07882c628609db8d1dcac196df0a 59.085534605000 639666 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": 306799, "vin": [ { "gen": { "height": 306789 } } ], "vout": [ { "amount": 59085534605, "target": { "key": "b8211b3018dd0e23161e946137a2191e1b0e07882c628609db8d1dcac196df0a" } } ], "extra": [ 1, 120, 112, 156, 78, 107, 79, 121, 113, 236, 113, 141, 47, 238, 22, 200, 64, 84, 70, 192, 239, 233, 116, 244, 223, 212, 233, 125, 138, 248, 84, 1, 170, 2, 17, 0, 0, 0, 31, 88, 4, 94, 91, 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