Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb4680be0cefdf3df668718c79edadb117b2e36f725bdb7fdcd264a8a0957e7

Tx prefix hash: 19e52c5aabef0fd608bb46d672ee5564cd0c3052fef6a0a2f93f3044e6584fa7
Tx public key: 6fce08839e1374635edafe5b56fa634e0b7a7325da6fde7d60c101e976102ef0
Timestamp: 1724145737 Timestamp [UCT]: 2024-08-20 09:22:17 Age [y:d:h:m:s]: 00:298:21:12:45
Block: 1091934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213430 RingCT/type: yes/0
Extra: 016fce08839e1374635edafe5b56fa634e0b7a7325da6fde7d60c101e976102ef002110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 719a0e62dec7e2e20d022aaea8623a4c15168e75e5ffb12d1ecf139e5896819b 0.600000000000 1566579 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": 1091944, "vin": [ { "gen": { "height": 1091934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "719a0e62dec7e2e20d022aaea8623a4c15168e75e5ffb12d1ecf139e5896819b" } } ], "extra": [ 1, 111, 206, 8, 131, 158, 19, 116, 99, 94, 218, 254, 91, 86, 250, 99, 78, 11, 122, 115, 37, 218, 111, 222, 125, 96, 193, 1, 233, 118, 16, 46, 240, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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