Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0de5f74ccafb06d54f791e81d86a35f4b6e52e0296321caaedf70956998d434

Tx prefix hash: 52f8f22dd0aa1b363d2c78994cfc923f653eb370b21ee90b6b99b47c0fe21b0a
Tx public key: ac22670448d9058af16fec26a2ce504b800513e6a85c34ebf4af6bff217c90c3
Timestamp: 1715852728 Timestamp [UCT]: 2024-05-16 09:45:28 Age [y:d:h:m:s]: 00:326:05:26:12
Block: 1023175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233175 RingCT/type: yes/0
Extra: 01ac22670448d9058af16fec26a2ce504b800513e6a85c34ebf4af6bff217c90c302110000000579bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 799b3cdb40ad7f5cbdcf3f5da922f78e9676dc6dac0c8eb0cd385f47010ae6b5 0.600000000000 1487992 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": 1023185, "vin": [ { "gen": { "height": 1023175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "799b3cdb40ad7f5cbdcf3f5da922f78e9676dc6dac0c8eb0cd385f47010ae6b5" } } ], "extra": [ 1, 172, 34, 103, 4, 72, 217, 5, 138, 241, 111, 236, 38, 162, 206, 80, 75, 128, 5, 19, 230, 168, 92, 52, 235, 244, 175, 107, 255, 33, 124, 144, 195, 2, 17, 0, 0, 0, 5, 121, 189, 163, 190, 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