Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea43ddd05b415da552c9c56abb9b45d0ce451e759d20a3627aafd813626be756

Tx prefix hash: 8e707b01855f737094bf31ef135a39635629a60dc318af25914fe45c0363d48e
Tx public key: 42e77e3ee3e64fdf0bf5e74749bc6a4d899bb9314f167de51d9af7f3adf30eee
Timestamp: 1766206672 Timestamp [UCT]: 2025-12-20 04:57:52 Age [y:d:h:m:s]: 00:001:05:13:06
Block: 1437494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 867 RingCT/type: yes/0
Extra: 0142e77e3ee3e64fdf0bf5e74749bc6a4d899bb9314f167de51d9af7f3adf30eee0211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f5520623718fb7cb4e3b3ba4d66fdf5161a1e100e8cae8925ab1b4470d16150 0.600000000000 1926303 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": 1437504, "vin": [ { "gen": { "height": 1437494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f5520623718fb7cb4e3b3ba4d66fdf5161a1e100e8cae8925ab1b4470d16150" } } ], "extra": [ 1, 66, 231, 126, 62, 227, 230, 79, 223, 11, 245, 231, 71, 73, 188, 106, 77, 137, 155, 185, 49, 79, 22, 125, 229, 29, 154, 247, 243, 173, 243, 14, 238, 2, 17, 0, 0, 0, 3, 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