Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8341ece8f0f117fdb0f52c17ad0c03df77816bc78f91d61d421861d5aa1c0e63

Tx prefix hash: a3ee2aedfda99e8b622a191b4920479103f62a191f585a17929f799d86cd3f16
Tx public key: 8ae0ba2e43a5aea4ef825ab0e946e8c501c422e482db005aaaad87def2073653
Timestamp: 1759473680 Timestamp [UTC]: 2025-10-03 06:41:20 Age [y:d:h:m:s]: 00:325:23:53:52
Block: 1381689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238816 RingCT/type: yes/0
Extra: 018ae0ba2e43a5aea4ef825ab0e946e8c501c422e482db005aaaad87def207365302110000000597baf922000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b94c2cfda767e51369bf086637dc1192ee184c375a458fb8e16d5b8a7d9e96a4 0.000600000000 1869808 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": 1381699, "vin": [ { "gen": { "height": 1381689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b94c2cfda767e51369bf086637dc1192ee184c375a458fb8e16d5b8a7d9e96a4" } } ], "extra": [ 1, 138, 224, 186, 46, 67, 165, 174, 164, 239, 130, 90, 176, 233, 70, 232, 197, 1, 196, 34, 228, 130, 219, 0, 90, 170, 173, 135, 222, 242, 7, 54, 83, 2, 17, 0, 0, 0, 5, 151, 186, 249, 34, 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: