Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aedc840265d35f5698a9b4633ffe7a244061687c236cfa854907b8c434e30438

Tx prefix hash: e106bad22a1086887cd096ceae98e663fbe7dcb3d1ea70856aeddea9155d22b0
Tx public key: 0b3b878bcc6992ced8795a9817defb948565ac237c843c0a633a47d4de31f7dd
Timestamp: 1729964635 Timestamp [UCT]: 2024-10-26 17:43:55 Age [y:d:h:m:s]: 00:180:20:26:40
Block: 1140140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129066 RingCT/type: yes/0
Extra: 010b3b878bcc6992ced8795a9817defb948565ac237c843c0a633a47d4de31f7dd0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3965c2db9ec67f93cebaa98c8c0fa7d6382db6cb67a90a5f62e2e679861d13b8 0.600000000000 1623935 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": 1140150, "vin": [ { "gen": { "height": 1140140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3965c2db9ec67f93cebaa98c8c0fa7d6382db6cb67a90a5f62e2e679861d13b8" } } ], "extra": [ 1, 11, 59, 135, 139, 204, 105, 146, 206, 216, 121, 90, 152, 23, 222, 251, 148, 133, 101, 172, 35, 124, 132, 60, 10, 99, 58, 71, 212, 222, 49, 247, 221, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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