Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccae43cd3a234a1965a1a9346b97b71385ecc9ce0a90435515656e4abd4da3e4

Tx prefix hash: 9db2dad2725af7f954cfcd9dfb6210cdcae0db8b6fc7e83e36268f33e5d124cb
Tx public key: a911ef47b2a39cc2d1e3dfaf85f5638cd6fa0262e50b6b17af7049a9a7e03751
Timestamp: 1699881762 Timestamp [UCT]: 2023-11-13 13:22:42 Age [y:d:h:m:s]: 01:127:04:47:06
Block: 890770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352099 RingCT/type: yes/0
Extra: 01a911ef47b2a39cc2d1e3dfaf85f5638cd6fa0262e50b6b17af7049a9a7e03751021100000003faf35c9c000000000000000000

1 output(s) for total of 0.686292433000 dcy

stealth address amount amount idx
00: 0a58e7f6ac266bfdb1297c0201808d9adc3b0cc44a30fd39c326eeaf0291b8e5 0.686292433000 1346801 of 0

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": 890780, "vin": [ { "gen": { "height": 890770 } } ], "vout": [ { "amount": 686292433, "target": { "key": "0a58e7f6ac266bfdb1297c0201808d9adc3b0cc44a30fd39c326eeaf0291b8e5" } } ], "extra": [ 1, 169, 17, 239, 71, 178, 163, 156, 194, 209, 227, 223, 175, 133, 245, 99, 140, 214, 250, 2, 98, 229, 11, 107, 23, 175, 112, 73, 169, 167, 224, 55, 81, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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