Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 070fbc1b0acf0865967d572a32475c272c321f263b2a27536a6c610d42f84e7c

Tx prefix hash: 2ec2b03318f943affc4c27207d34aa94623d0dc6e0985737902620b95f4ae50e
Tx public key: 33a77720a85524031dee11e604d1927cc0ef1f13a71f77b85a2c5d8d40976717
Timestamp: 1711166619 Timestamp [UTC]: 2024-03-23 04:03:39 Age [y:d:h:m:s]: 02:158:08:36:44
Block: 984340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 638541 RingCT/type: yes/0
Extra: 0133a77720a85524031dee11e604d1927cc0ef1f13a71f77b85a2c5d8d409767170211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 49bc769b4749f014107a192d647c2dedaac2d893a1cc5d250fdaa55f9ebe92fc 0.000600000000 1444511 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": 984350, "vin": [ { "gen": { "height": 984340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49bc769b4749f014107a192d647c2dedaac2d893a1cc5d250fdaa55f9ebe92fc" } } ], "extra": [ 1, 51, 167, 119, 32, 168, 85, 36, 3, 29, 238, 17, 230, 4, 209, 146, 124, 192, 239, 31, 19, 167, 31, 119, 184, 90, 44, 93, 141, 64, 151, 103, 23, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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: