Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d05063f0cf4e03c6f1fef749f1d2b07677fd87205a55c2d4ca4e0c99cd1475d

Tx prefix hash: bba11cd67aef4389dd58c0be99c3b9aab0ac0e77fcf95d03555419d1ffb9edd4
Tx public key: 58d460f293f6b27b559a1f8dfbb9f5ead2f51c00fd400bc487a3d8cb9df288ff
Timestamp: 1772011933 Timestamp [UTC]: 2026-02-25 09:32:13 Age [y:d:h:m:s]: 00:267:23:36:43
Block: 1485436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197127 RingCT/type: yes/0
Extra: 0158d460f293f6b27b559a1f8dfbb9f5ead2f51c00fd400bc487a3d8cb9df288ff021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aaf8c6b0f8adb56081f4cdd19a510b7469eae60094a678e587449916be61440a 0.000600000000 1974872 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": 1485446, "vin": [ { "gen": { "height": 1485436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaf8c6b0f8adb56081f4cdd19a510b7469eae60094a678e587449916be61440a" } } ], "extra": [ 1, 88, 212, 96, 242, 147, 246, 178, 123, 85, 154, 31, 141, 251, 185, 245, 234, 210, 245, 28, 0, 253, 64, 11, 196, 135, 163, 216, 203, 157, 242, 136, 255, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 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: