Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7b7caed2d5ff037f25bb68c1eb8e049358a7a641a9c4c84dda56696806d9557

Tx prefix hash: 8d4d4e05076fbdb99a64ec671d99e2aa580477e66a4051fcf0dff058956bebd5
Tx public key: 86b850593be97007156a8b2c316e8e876d3b74edea1a1d29d784fc4b44a6f15f
Timestamp: 1722347162 Timestamp [UCT]: 2024-07-30 13:46:02 Age [y:d:h:m:s]: 00:258:23:39:13
Block: 1077011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185005 RingCT/type: yes/0
Extra: 0186b850593be97007156a8b2c316e8e876d3b74edea1a1d29d784fc4b44a6f15f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd84d6a354e9a798e716187e55000d40d9eb4f513d883cc02a3d06d4c3bcd2c9 0.600000000000 1549554 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": 1077021, "vin": [ { "gen": { "height": 1077011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd84d6a354e9a798e716187e55000d40d9eb4f513d883cc02a3d06d4c3bcd2c9" } } ], "extra": [ 1, 134, 184, 80, 89, 59, 233, 112, 7, 21, 106, 139, 44, 49, 110, 142, 135, 109, 59, 116, 237, 234, 26, 29, 41, 215, 132, 252, 75, 68, 166, 241, 95, 2, 17, 0, 0, 0, 2, 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