Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28fedc49da2f49399f47505ad69825c7c68326e704c798be4617c99443220e81

Tx prefix hash: 7dc9aab200769190085435366b41c782904e65a5e83bc3ae429118b1a9bce642
Tx public key: 024dc01ff3ba4b0f03e42b6fdf387aecf1cca85748afde190af79f36c442a323
Timestamp: 1705484282 Timestamp [UTC]: 2024-01-17 09:38:02 Age [y:d:h:m:s]: 02:017:11:46:42
Block: 937199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 532120 RingCT/type: yes/0
Extra: 01024dc01ff3ba4b0f03e42b6fdf387aecf1cca85748afde190af79f36c442a3230211000000020011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c0b40365f41f6406830d8dae54699e56b1aef884d3827d6103a6e1676f44b417 0.000600000000 1395243 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": 937209, "vin": [ { "gen": { "height": 937199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0b40365f41f6406830d8dae54699e56b1aef884d3827d6103a6e1676f44b417" } } ], "extra": [ 1, 2, 77, 192, 31, 243, 186, 75, 15, 3, 228, 43, 111, 223, 56, 122, 236, 241, 204, 168, 87, 72, 175, 222, 25, 10, 247, 159, 54, 196, 66, 163, 35, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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) | dinastycoin version: tesla-369