Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 821b307fc3317b86e1ef399b198edfbc89644be066e8684af83b916b316b6a5c

Tx prefix hash: 4121563069b0610841ba447c0cf6067d8e12f346af5b885507568cd99211f796
Tx public key: 6f055a7b3049724f0261de16b7b8f9f71083255b1680e0c7063046a16d71e349
Timestamp: 1714335150 Timestamp [UCT]: 2024-04-28 20:12:30 Age [y:d:h:m:s]: 01:194:09:38:39
Block: 1010585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397579 RingCT/type: yes/0
Extra: 016f055a7b3049724f0261de16b7b8f9f71083255b1680e0c7063046a16d71e34902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdb47d1cae15a621d4c1c1cc99849036f327f805b928ac69ebdea97e74c218ab 0.600000000000 1472583 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": 1010595, "vin": [ { "gen": { "height": 1010585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdb47d1cae15a621d4c1c1cc99849036f327f805b928ac69ebdea97e74c218ab" } } ], "extra": [ 1, 111, 5, 90, 123, 48, 73, 114, 79, 2, 97, 222, 22, 183, 184, 249, 247, 16, 131, 37, 91, 22, 128, 224, 199, 6, 48, 70, 161, 109, 113, 227, 73, 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