Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f59287c8c9d6fd2c34ac30bc33b58ba24b5aefa4f9cb7301627729e970bd1f72

Tx prefix hash: d61642085b5d31f29f8aebde5e165a8638b744e670e4d4db12acc3317858b5aa
Tx public key: b7a3691bb16ad71573f59a5374ec4fb8f06f4e79e03580388adc2c2b1f76386b
Timestamp: 1753941117 Timestamp [UTC]: 2025-07-31 05:51:57 Age [y:d:h:m:s]: 00:354:16:15:37
Block: 1337124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245990 RingCT/type: yes/0
Extra: 01b7a3691bb16ad71573f59a5374ec4fb8f06f4e79e03580388adc2c2b1f76386b021100000001b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1d2d346a1834b883612e89e86b753a8e805ebaa4fe76c4e1df0bb19dc32f0f22 0.000600000000 1824927 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": 1337134, "vin": [ { "gen": { "height": 1337124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d2d346a1834b883612e89e86b753a8e805ebaa4fe76c4e1df0bb19dc32f0f22" } } ], "extra": [ 1, 183, 163, 105, 27, 177, 106, 215, 21, 115, 245, 154, 83, 116, 236, 79, 184, 240, 111, 78, 121, 224, 53, 128, 56, 138, 220, 44, 43, 31, 118, 56, 107, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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: