Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c76c099db0042271a181705660e1a2c75da0758a6f2da4a54480c25725d0e776

Tx prefix hash: 6017f9abc3990935549b88274d49d51b4d748c768bcd892dca6b654c680b79f7
Tx public key: 384d32f586c1a1dab374bd7be467fbf0c336acd6e5a828f01d711e7a2de20c5d
Timestamp: 1730817713 Timestamp [UCT]: 2024-11-05 14:41:53 Age [y:d:h:m:s]: 01:009:03:27:00
Block: 1147146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264969 RingCT/type: yes/0
Extra: 01384d32f586c1a1dab374bd7be467fbf0c336acd6e5a828f01d711e7a2de20c5d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4de919038be3bffc83b560a271a12318248ab5b31ef773766a80cb2ad870b883 0.600000000000 1631839 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": 1147156, "vin": [ { "gen": { "height": 1147146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4de919038be3bffc83b560a271a12318248ab5b31ef773766a80cb2ad870b883" } } ], "extra": [ 1, 56, 77, 50, 245, 134, 193, 161, 218, 179, 116, 189, 123, 228, 103, 251, 240, 195, 54, 172, 214, 229, 168, 40, 240, 29, 113, 30, 122, 45, 226, 12, 93, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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