Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e213e40039c1b96328ef9899a04653e9d2fba9e96c0e8f1cc7ecf4f0a187ee3

Tx prefix hash: 4ffb2543ffc91fdbf1f83b2604ee10e5729ce39b0b2d40ee799846a361743efc
Tx public key: 014d4090128279905dd635a87cc626f5e3cd2d28fd9bc2643f8a162bf70c8fbd
Timestamp: 1766256269 Timestamp [UCT]: 2025-12-20 18:44:29 Age [y:d:h:m:s]: 00:002:12:55:19
Block: 1437907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1814 RingCT/type: yes/0
Extra: 01014d4090128279905dd635a87cc626f5e3cd2d28fd9bc2643f8a162bf70c8fbd02110000000a7b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3b8816561cdf2b443a0a44892f2bf177f0fb283a246737aff8eda1ceaf79272 0.600000000000 1926720 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": 1437917, "vin": [ { "gen": { "height": 1437907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3b8816561cdf2b443a0a44892f2bf177f0fb283a246737aff8eda1ceaf79272" } } ], "extra": [ 1, 1, 77, 64, 144, 18, 130, 121, 144, 93, 214, 53, 168, 124, 198, 38, 245, 227, 205, 45, 40, 253, 155, 194, 100, 63, 138, 22, 43, 247, 12, 143, 189, 2, 17, 0, 0, 0, 10, 123, 30, 81, 172, 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