Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e727cbdf5bea8ab562f0a1a09d9dcde3fce4d77b409ff69398cd217d62994f91

Tx prefix hash: bb78cef40649b8ddf4280dd9d7e55d02f55de3350662fb2be46510a7f2f4dc56
Tx public key: 049f1fb0fa43fbb5eec7e338311fd4114963985a5c9b4a9af7cce3d88b749371
Timestamp: 1764465837 Timestamp [UTC]: 2025-11-30 01:23:57 Age [y:d:h:m:s]: 00:349:20:57:36
Block: 1423067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255372 RingCT/type: yes/0
Extra: 01049f1fb0fa43fbb5eec7e338311fd4114963985a5c9b4a9af7cce3d88b74937102110000000417b19132000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6c01e98e84193a88bcdbe02ce38098bf1c7a4998f4e5d7e3f8e0c0a4270a656a 0.000600000000 1911670 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 dinastycoin-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": 1423077, "vin": [ { "gen": { "height": 1423067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c01e98e84193a88bcdbe02ce38098bf1c7a4998f4e5d7e3f8e0c0a4270a656a" } } ], "extra": [ 1, 4, 159, 31, 176, 250, 67, 251, 181, 238, 199, 227, 56, 49, 31, 212, 17, 73, 99, 152, 90, 92, 155, 74, 154, 247, 204, 227, 216, 139, 116, 147, 113, 2, 17, 0, 0, 0, 4, 23, 177, 145, 50, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: