Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f1a80d9ffe10753e3a3c874fd3cc621f9899398055e26e87ff9128a287269ed

Tx prefix hash: a4a57ecba5f9b6f97d4a30706deb42982ec39816d8e8e0f2a372df0688f2e394
Tx public key: 310bf0bdbf850eb77010a8f8c886d7b3422f784f61fb6cfd957f4d882a35255f
Timestamp: 1709275525 Timestamp [UCT]: 2024-03-01 06:45:25 Age [y:d:h:m:s]: 00:342:04:03:49
Block: 968656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244659 RingCT/type: yes/0
Extra: 01310bf0bdbf850eb77010a8f8c886d7b3422f784f61fb6cfd957f4d882a35255f0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21a3a1defd80d16393111ef5cc2096f50787d756e51f2a3e2ed58c59c344d395 0.600000000000 1428473 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": 968666, "vin": [ { "gen": { "height": 968656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21a3a1defd80d16393111ef5cc2096f50787d756e51f2a3e2ed58c59c344d395" } } ], "extra": [ 1, 49, 11, 240, 189, 191, 133, 14, 183, 112, 16, 168, 248, 200, 134, 215, 179, 66, 47, 120, 79, 97, 251, 108, 253, 149, 127, 77, 136, 42, 53, 37, 95, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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