Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eea0beaf541205376ad40e5883d1a4263e7015db7efb82516de52971fb79dde6

Tx prefix hash: 8066ae5bca1bcb0c3c302b1fb07b6c8bed0f2ea362a0e946312f762dff93fc74
Tx public key: ad3a6411def9f844224c671fd1399485de90b3a0c4a94c050e388bb39966c5cf
Timestamp: 1627546851 Timestamp [UCT]: 2021-07-29 08:20:51 Age [y:d:h:m:s]: 03:164:13:03:19
Block: 303024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 890117 RingCT/type: yes/0
Extra: 01ad3a6411def9f844224c671fd1399485de90b3a0c4a94c050e388bb39966c5cf0211000000186af0ff51000000000000000000

1 output(s) for total of 60.807364793000 dcy

stealth address amount amount idx
00: 8224d5bdc3d8f7a67e1c4b7efae142d1ed4fb6d2fcab0c98b41bff48fd8a197b 60.807364793000 632557 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": 303034, "vin": [ { "gen": { "height": 303024 } } ], "vout": [ { "amount": 60807364793, "target": { "key": "8224d5bdc3d8f7a67e1c4b7efae142d1ed4fb6d2fcab0c98b41bff48fd8a197b" } } ], "extra": [ 1, 173, 58, 100, 17, 222, 249, 248, 68, 34, 76, 103, 31, 209, 57, 148, 133, 222, 144, 179, 160, 196, 169, 76, 5, 14, 56, 139, 179, 153, 102, 197, 207, 2, 17, 0, 0, 0, 24, 106, 240, 255, 81, 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