Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b455ea0c8b9876e250b39c2f328efa837c03e4035aca9c36090285966943397

Tx prefix hash: 6dc1a90c5f38eb843d80f0aa12bd2441717f4b2220dace0485e021b24d2c4ba9
Tx public key: 49bb4aa4faf8906769d966d29f063d65ae891bfc58f62d31e794af7496eb1e03
Timestamp: 1704297823 Timestamp [UTC]: 2024-01-03 16:03:43 Age [y:d:h:m:s]: 02:136:22:57:23
Block: 927391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 610936 RingCT/type: yes/0
Extra: 0149bb4aa4faf8906769d966d29f063d65ae891bfc58f62d31e794af7496eb1e03021100000002e08532b6000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: df9140c165e14a47021d33fe867414c6b822682a29de1dccb63f796ab273fddd 0.000600000000 1385227 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": 927401, "vin": [ { "gen": { "height": 927391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df9140c165e14a47021d33fe867414c6b822682a29de1dccb63f796ab273fddd" } } ], "extra": [ 1, 73, 187, 74, 164, 250, 248, 144, 103, 105, 217, 102, 210, 159, 6, 61, 101, 174, 137, 27, 252, 88, 246, 45, 49, 231, 148, 175, 116, 150, 235, 30, 3, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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: