Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbc58dbf01f6618abb272e05a3007e58257654b0573b14bad6d63a7dc7cb3d08

Tx prefix hash: 2c7dd234d9a079c7de21ab40d3bd21f06044883f2d5dfe6bd4cbcb7f04981341
Tx public key: 1fbd924e51a4b21dc8ee90d8fc366d8ee5be4ded2954a4a66a7ad546cb27bfab
Timestamp: 1694469029 Timestamp [UCT]: 2023-09-11 21:50:29 Age [y:d:h:m:s]: 01:224:17:53:33
Block: 846072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421738 RingCT/type: yes/0
Extra: 011fbd924e51a4b21dc8ee90d8fc366d8ee5be4ded2954a4a66a7ad546cb27bfab02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.965188870000 dcy

stealth address amount amount idx
00: a78f6a3d5febeb9102366e08f87ae74a53cb430feb018731b464a737b663c1d9 0.965188870000 1299514 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": 846082, "vin": [ { "gen": { "height": 846072 } } ], "vout": [ { "amount": 965188870, "target": { "key": "a78f6a3d5febeb9102366e08f87ae74a53cb430feb018731b464a737b663c1d9" } } ], "extra": [ 1, 31, 189, 146, 78, 81, 164, 178, 29, 200, 238, 144, 216, 252, 54, 109, 142, 229, 190, 77, 237, 41, 84, 164, 166, 106, 122, 213, 70, 203, 39, 191, 171, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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