Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80160aedc5679a75dddf4bcafb250fe815e8df1142cd5d226ae1f663825f3f12

Tx prefix hash: bff6161202993559f7d80c627a51ef8d119e91d76d6827e5514a62255f360c17
Tx public key: 5e14c6f195b6e9717e72d6ee366ee0fa10e8869dd2c479c9faa504d110dcbef4
Timestamp: 1731303073 Timestamp [UCT]: 2024-11-11 05:31:13 Age [y:d:h:m:s]: 00:013:01:07:14
Block: 1151167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9339 RingCT/type: yes/0
Extra: 015e14c6f195b6e9717e72d6ee366ee0fa10e8869dd2c479c9faa504d110dcbef4021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a2c1a0480c9b30dc71165dcea59f8e1ed0ac6810506b8b18995d37fb86b91c9 0.600000000000 1636644 of 15

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": 1151177, "vin": [ { "gen": { "height": 1151167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a2c1a0480c9b30dc71165dcea59f8e1ed0ac6810506b8b18995d37fb86b91c9" } } ], "extra": [ 1, 94, 20, 198, 241, 149, 182, 233, 113, 126, 114, 214, 238, 54, 110, 224, 250, 16, 232, 134, 157, 210, 196, 121, 201, 250, 165, 4, 209, 16, 220, 190, 244, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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