Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b8ec6333e5a51edad7bc48e2aff3e0aca94f7eefaad45134379b3697cd983f2

Tx prefix hash: 042ed82498c9be8e5cb3d64e0fd5d616a00fb4b31889aa6d41643c7c5a94e85b
Tx public key: 21b56481d1af0ce9b5ea09c3d6b9af9c26d8cc9f72a5f31c0506d13e9b6074c6
Timestamp: 1718060075 Timestamp [UCT]: 2024-06-10 22:54:35 Age [y:d:h:m:s]: 00:134:10:43:23
Block: 1041485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96259 RingCT/type: yes/0
Extra: 0121b56481d1af0ce9b5ea09c3d6b9af9c26d8cc9f72a5f31c0506d13e9b6074c60211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96c3fc3760a4ded9f608947fb42905a3da64ceb8ba97ea9de0d0dee469ab21c0 0.600000000000 1510172 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": 1041495, "vin": [ { "gen": { "height": 1041485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96c3fc3760a4ded9f608947fb42905a3da64ceb8ba97ea9de0d0dee469ab21c0" } } ], "extra": [ 1, 33, 181, 100, 129, 209, 175, 12, 233, 181, 234, 9, 195, 214, 185, 175, 156, 38, 216, 204, 159, 114, 165, 243, 28, 5, 6, 209, 62, 155, 96, 116, 198, 2, 17, 0, 0, 0, 3, 0, 17, 5, 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