Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fac5f75e9e4a337db8fc60285a84d394b9b510c03b830a5f18d681dbbcff9f1

Tx prefix hash: 353372c5f3c6df4b7fd1674e9b05c09270a9c38799f72028467a90076d38b95a
Tx public key: f3eba89214d1ee813078ead5fcb9eca8025b1b32b0691d056068d4f4645fd6cd
Timestamp: 1744199259 Timestamp [UTC]: 2025-04-09 11:47:39 Age [y:d:h:m:s]: 01:224:00:44:43
Block: 1257686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424197 RingCT/type: yes/0
Extra: 01f3eba89214d1ee813078ead5fcb9eca8025b1b32b0691d056068d4f4645fd6cd0211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c59a54fe31a0d795e8cf962b6cf241857292fc2409485a5fcfeaac427ea5711b 0.000600000000 1744815 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": 1257696, "vin": [ { "gen": { "height": 1257686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c59a54fe31a0d795e8cf962b6cf241857292fc2409485a5fcfeaac427ea5711b" } } ], "extra": [ 1, 243, 235, 168, 146, 20, 209, 238, 129, 48, 120, 234, 213, 252, 185, 236, 168, 2, 91, 27, 50, 176, 105, 29, 5, 96, 104, 212, 244, 100, 95, 214, 205, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: