Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e5f2e38e8b155a0e27b1e5b49f93d1d0f1b1c31140275ee65a3a570f7734d49

Tx prefix hash: 615a3520a1f3c5767285976475b3aa7af57dc08a56298fec2e46ded94961d226
Tx public key: 911cd517464c899785379c0553d1e84ee3d4d49a8e208e2324e7d05ff32b2018
Timestamp: 1703155084 Timestamp [UCT]: 2023-12-21 10:38:04 Age [y:d:h:m:s]: 01:182:22:29:17
Block: 917904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391744 RingCT/type: yes/0
Extra: 01911cd517464c899785379c0553d1e84ee3d4d49a8e208e2324e7d05ff32b201802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f2f03ab1fe8fab43fcc37b38cb0b59b96b5cae1cf4ac91055c6bd922d94a908 0.600000000000 1375528 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": 917914, "vin": [ { "gen": { "height": 917904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f2f03ab1fe8fab43fcc37b38cb0b59b96b5cae1cf4ac91055c6bd922d94a908" } } ], "extra": [ 1, 145, 28, 213, 23, 70, 76, 137, 151, 133, 55, 156, 5, 83, 209, 232, 78, 227, 212, 212, 154, 142, 32, 142, 35, 36, 231, 208, 95, 243, 43, 32, 24, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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