Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a06acf776be654a3dce49f177f4490b1e5023442683178b002762e3e215188b9

Tx prefix hash: baaa7a427f798392780293681bea98b232ad134a0082b3d038416f8b1ed7ea5d
Tx public key: 25d48f604c1a3b87d3e4b82d8c00b9b10a094b2086922684c67f2140254a94d3
Timestamp: 1710351609 Timestamp [UCT]: 2024-03-13 17:40:09 Age [y:d:h:m:s]: 01:075:19:31:35
Block: 977582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315206 RingCT/type: yes/0
Extra: 0125d48f604c1a3b87d3e4b82d8c00b9b10a094b2086922684c67f2140254a94d302110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4a9df4792c677d82d7e228fbc21ba243542a8c770ac92e4a1ff6539962db0fc 0.600000000000 1437585 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": 977592, "vin": [ { "gen": { "height": 977582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4a9df4792c677d82d7e228fbc21ba243542a8c770ac92e4a1ff6539962db0fc" } } ], "extra": [ 1, 37, 212, 143, 96, 76, 26, 59, 135, 211, 228, 184, 45, 140, 0, 185, 177, 10, 9, 75, 32, 134, 146, 38, 132, 198, 127, 33, 64, 37, 74, 148, 211, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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