Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6312e4862f99b7503d1f514d8371221fe70df4493714ac93c534abbd541b8f93

Tx prefix hash: 40659a09ec6c324e577d20e095933d6e9623d46b15c558d4c4a782dafc3cbf65
Tx public key: 478306b4fc589dc9232871a9aee9ab26c9e5757516e1ecbe18433962fd8e06a4
Timestamp: 1720225374 Timestamp [UCT]: 2024-07-06 00:22:54 Age [y:d:h:m:s]: 00:272:01:09:40
Block: 1059413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194380 RingCT/type: yes/0
Extra: 01478306b4fc589dc9232871a9aee9ab26c9e5757516e1ecbe18433962fd8e06a402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2300c073a292fab1456be227248ec5b5b16a28b2ae2b29cfb8311436cc23e72 0.600000000000 1529882 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": 1059423, "vin": [ { "gen": { "height": 1059413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2300c073a292fab1456be227248ec5b5b16a28b2ae2b29cfb8311436cc23e72" } } ], "extra": [ 1, 71, 131, 6, 180, 252, 88, 157, 201, 35, 40, 113, 169, 174, 233, 171, 38, 201, 229, 117, 117, 22, 225, 236, 190, 24, 67, 57, 98, 253, 142, 6, 164, 2, 17, 0, 0, 0, 2, 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