Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4891dfa405de8b36e2eebe0da103ff0aa2b5b01bd6a396d293e05930b6620097

Tx prefix hash: b49ee16264fac3157c80876dc8794d08d374cd5f8feb8811fb1aa286918be0d2
Tx public key: 3a3ca4819d5486dcc5b51790e01433c0ee27e0c38bbe71c9b6b3f67a40feeb36
Timestamp: 1732542329 Timestamp [UCT]: 2024-11-25 13:45:29 Age [y:d:h:m:s]: 00:346:11:42:51
Block: 1161441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245154 RingCT/type: yes/0
Extra: 013a3ca4819d5486dcc5b51790e01433c0ee27e0c38bbe71c9b6b3f67a40feeb36021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 980bf03d402dc24fa5bd744e838097d7356e2bdda620dc45e61fa6e8c6132353 0.600000000000 1647096 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": 1161451, "vin": [ { "gen": { "height": 1161441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "980bf03d402dc24fa5bd744e838097d7356e2bdda620dc45e61fa6e8c6132353" } } ], "extra": [ 1, 58, 60, 164, 129, 157, 84, 134, 220, 197, 181, 23, 144, 224, 20, 51, 192, 238, 39, 224, 195, 139, 190, 113, 201, 182, 179, 246, 122, 64, 254, 235, 54, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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