Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d5a83ae10eb6cccf3758e962223fba8ad2d0a2189eddb98e7f53db78ef5db5f

Tx prefix hash: 80edcc4fe61d68edae33f7ec8bff690aea8e4d45a85c423696ece2672dc7af46
Tx public key: 020bcdf3b95a29d50901ac45bd1dbeb4d12bbde665cd9ca1ca0948cbbf85ac20
Timestamp: 1696812026 Timestamp [UCT]: 2023-10-09 00:40:26 Age [y:d:h:m:s]: 01:090:02:49:50
Block: 865527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325660 RingCT/type: yes/0
Extra: 01020bcdf3b95a29d50901ac45bd1dbeb4d12bbde665cd9ca1ca0948cbbf85ac2002110000000141ee1c9b000000000000000000

1 output(s) for total of 0.832050691000 dcy

stealth address amount amount idx
00: 3a7d1796a6f2e43bc69a0a5dcd6bccce7bc1df09ac95ea3b0452758c4dc76854 0.832050691000 1320063 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": 865537, "vin": [ { "gen": { "height": 865527 } } ], "vout": [ { "amount": 832050691, "target": { "key": "3a7d1796a6f2e43bc69a0a5dcd6bccce7bc1df09ac95ea3b0452758c4dc76854" } } ], "extra": [ 1, 2, 11, 205, 243, 185, 90, 41, 213, 9, 1, 172, 69, 189, 29, 190, 180, 209, 43, 189, 230, 101, 205, 156, 161, 202, 9, 72, 203, 191, 133, 172, 32, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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