Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06fc55bea6d8520c63ed800aedb3b92cad593342edbba46e52a538ea3ddb97f4

Tx prefix hash: 96214da37de11d13bb54d5fe47aeadab444d0a835feb18e893bf8049066b11b7
Tx public key: 053e05e9834cb8be91696e2fd5b9bbaf0f1f64fbd9352649f646690f1a0e3fc6
Timestamp: 1720878150 Timestamp [UCT]: 2024-07-13 13:42:30 Age [y:d:h:m:s]: 00:225:10:05:27
Block: 1064849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160989 RingCT/type: yes/0
Extra: 01053e05e9834cb8be91696e2fd5b9bbaf0f1f64fbd9352649f646690f1a0e3fc602110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a57e2484388897fa6b327212e0fa7f45b4da5f9805e06ba29b1f05422a193dcb 0.600000000000 1535388 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": 1064859, "vin": [ { "gen": { "height": 1064849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a57e2484388897fa6b327212e0fa7f45b4da5f9805e06ba29b1f05422a193dcb" } } ], "extra": [ 1, 5, 62, 5, 233, 131, 76, 184, 190, 145, 105, 110, 47, 213, 185, 187, 175, 15, 31, 100, 251, 217, 53, 38, 73, 246, 70, 105, 15, 26, 14, 63, 198, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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