Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d289e9039ef392aa3595ad022e8f136e0787d8f8fc0f36c4deaad1b86ada607c

Tx prefix hash: 45fa690ad6ed8f18a03f09ca8be886254477cd6314c7804d1c43160d0935a50d
Tx public key: 6fd11515fc31c5bbd086827e1acf452d480e40296e5028f4b4b6b15ea49019f9
Timestamp: 1769844998 Timestamp [UTC]: 2026-01-31 07:36:38 Age [y:d:h:m:s]: 00:100:23:20:58
Block: 1467462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64457 RingCT/type: yes/0
Extra: 016fd11515fc31c5bbd086827e1acf452d480e40296e5028f4b4b6b15ea49019f902110000000a49d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2408421828979786777b0c63c686f55c2e855f53c2c811b78d50ff233fa0d9bc 0.000600000000 1956702 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": 1467472, "vin": [ { "gen": { "height": 1467462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2408421828979786777b0c63c686f55c2e855f53c2c811b78d50ff233fa0d9bc" } } ], "extra": [ 1, 111, 209, 21, 21, 252, 49, 197, 187, 208, 134, 130, 126, 26, 207, 69, 45, 72, 14, 64, 41, 110, 80, 40, 244, 180, 182, 177, 94, 164, 144, 25, 249, 2, 17, 0, 0, 0, 10, 73, 215, 62, 152, 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: