Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb5b2b944d46818ba1c1b111675a805c98992393a5c3793cd3baa0e3098a887e

Tx prefix hash: 1654bdd1d83ba14690b9d25378a312f76d8c3a1266819ddf3c0fd8a717006138
Tx public key: ca2ff8d482b028a043948b9b8483be7d4c7cfc324ad5d76e68c9f52ee4cf254d
Timestamp: 1577402970 Timestamp [UCT]: 2019-12-26 23:29:30 Age [y:d:h:m:s]: 04:186:00:28:14
Block: 32507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1021890 RingCT/type: yes/0
Extra: 01ca2ff8d482b028a043948b9b8483be7d4c7cfc324ad5d76e68c9f52ee4cf254d0211000000058a2ee0d9000000000000000000

1 output(s) for total of 478.962039516000 dcy

stealth address amount amount idx
00: 90d3e0f10f0575ef2faf19b7bcc25efcf6386db9969d5aba45de817511208727 478.962039516000 54073 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": 32517, "vin": [ { "gen": { "height": 32507 } } ], "vout": [ { "amount": 478962039516, "target": { "key": "90d3e0f10f0575ef2faf19b7bcc25efcf6386db9969d5aba45de817511208727" } } ], "extra": [ 1, 202, 47, 248, 212, 130, 176, 40, 160, 67, 148, 139, 155, 132, 131, 190, 125, 76, 124, 252, 50, 74, 213, 215, 110, 104, 201, 245, 46, 228, 207, 37, 77, 2, 17, 0, 0, 0, 5, 138, 46, 224, 217, 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