Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2548f0303f30e5c2fec3e2d2e06f976dd96ba3a4c5498070875ed0b72ad420e

Tx prefix hash: e2f1789ee0ab4e490daa3d577a73fa700797ef924228f947d6042d1a872f1e0a
Tx public key: 10c05e5faf3a910985f293a5d70b545348f4aad1cd86c60fa61d713b5f2a8528
Timestamp: 1745885179 Timestamp [UTC]: 2025-04-29 00:06:19 Age [y:d:h:m:s]: 01:207:10:17:35
Block: 1271649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411845 RingCT/type: yes/0
Extra: 0110c05e5faf3a910985f293a5d70b545348f4aad1cd86c60fa61d713b5f2a85280211000000051f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 436bb0054d7f7ab58e7df80268dae9af673010ff5973870eecf0083d402bc6a3 0.000600000000 1758916 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": 1271659, "vin": [ { "gen": { "height": 1271649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "436bb0054d7f7ab58e7df80268dae9af673010ff5973870eecf0083d402bc6a3" } } ], "extra": [ 1, 16, 192, 94, 95, 175, 58, 145, 9, 133, 242, 147, 165, 215, 11, 84, 83, 72, 244, 170, 209, 205, 134, 198, 15, 166, 29, 113, 59, 95, 42, 133, 40, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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: