Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec6e5b3a3273d4f6d14eeb6f1f64e5de27508d0419be2b90d594b03b8cf2e3a1

Tx prefix hash: 84b57aca34ff16b6d6d7d39a75771756525c92b19780869446c1f0d969736532
Tx public key: 65fdaaada431c9110e8f7f79a771d45b0445fce83d6ea975f11742ef984c03dc
Timestamp: 1760035023 Timestamp [UCT]: 2025-10-09 18:37:03 Age [y:d:h:m:s]: 00:088:03:20:13
Block: 1386343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63135 RingCT/type: yes/0
Extra: 0165fdaaada431c9110e8f7f79a771d45b0445fce83d6ea975f11742ef984c03dc02110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 310525ae7ec608b4b0c2b3bc11d1579561288b23f21d4633fbfad4a3455d7424 0.600000000000 1874508 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": 1386353, "vin": [ { "gen": { "height": 1386343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "310525ae7ec608b4b0c2b3bc11d1579561288b23f21d4633fbfad4a3455d7424" } } ], "extra": [ 1, 101, 253, 170, 173, 164, 49, 201, 17, 14, 143, 127, 121, 167, 113, 212, 91, 4, 69, 252, 232, 61, 110, 169, 117, 241, 23, 66, 239, 152, 76, 3, 220, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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