Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 975a6c2796ff58fa97a82ebec79095f4c7d567fc7ef2cda5c76a591e671d4751

Tx prefix hash: a3d215e0a3702863fc5bf2a5d9d883354771f5ca69aedcd78edb65749505856a
Tx public key: 29039fff1b39bb6e585353e8b1a95784eb542d55205c1c296427cb147be70db9
Timestamp: 1739895602 Timestamp [UTC]: 2025-02-18 16:20:02 Age [y:d:h:m:s]: 01:272:16:56:12
Block: 1222031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459001 RingCT/type: yes/0
Extra: 0129039fff1b39bb6e585353e8b1a95784eb542d55205c1c296427cb147be70db90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e8899f2d7034e3340d6e5a4ffcd51b56ab2f2d7357673bf9c03d93e582c54d0c 0.000600000000 1708878 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": 1222041, "vin": [ { "gen": { "height": 1222031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8899f2d7034e3340d6e5a4ffcd51b56ab2f2d7357673bf9c03d93e582c54d0c" } } ], "extra": [ 1, 41, 3, 159, 255, 27, 57, 187, 110, 88, 83, 83, 232, 177, 169, 87, 132, 235, 84, 45, 85, 32, 92, 28, 41, 100, 39, 203, 20, 123, 231, 13, 185, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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: