Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46c009c434f9575b0712ef67a5fbe464307e6bbac8a26167383071ec565605bb

Tx prefix hash: 4f26f8b21240baeeccc98bb618cbbc7dae4d28159e91d3f19516304f668aa185
Tx public key: 4eebc8aca3b9e0874f01c5dee2b409fd8808b50e1a32ed16ff98661ddbf5a7bb
Timestamp: 1744576628 Timestamp [UCT]: 2025-04-13 20:37:08 Age [y:d:h:m:s]: 00:220:11:41:55
Block: 1260807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155306 RingCT/type: yes/0
Extra: 014eebc8aca3b9e0874f01c5dee2b409fd8808b50e1a32ed16ff98661ddbf5a7bb0211000000076c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d717d8d2212735f8bca1a42cb8b6ad279d583c53e3ab09d703e739c1b67e4cc5 0.600000000000 1747970 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": 1260817, "vin": [ { "gen": { "height": 1260807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d717d8d2212735f8bca1a42cb8b6ad279d583c53e3ab09d703e739c1b67e4cc5" } } ], "extra": [ 1, 78, 235, 200, 172, 163, 185, 224, 135, 79, 1, 197, 222, 226, 180, 9, 253, 136, 8, 181, 14, 26, 50, 237, 22, 255, 152, 102, 29, 219, 245, 167, 187, 2, 17, 0, 0, 0, 7, 108, 152, 170, 61, 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