Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb0ef603ab5670f56ca0e6d0a15bc2b1d796e894930b3d447e78f145ba65f652

Tx prefix hash: 34f4bc2e92ffab931e73fc4791d1127e98052068fd68931bd8162e4f269c5d57
Tx public key: 54cb4974348c9245d96c8a3186b7d44b37f5205062d9da05f503b9db44d27fdb
Timestamp: 1574569685 Timestamp [UTC]: 2019-11-24 04:28:05 Age [y:d:h:m:s]: 06:362:05:37:18
Block: 16167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1665640 RingCT/type: yes/0
Extra: 0154cb4974348c9245d96c8a3186b7d44b37f5205062d9da05f503b9db44d27fdb021100000007f95225a5000000000000000000

1 output(s) for total of 0.542541420582 xmr

stealth address amount amount idx tag
00: 2948bc3ead56caecdcd1f88e91ec0d45dacf056a36ffa1d20dfad07a1e001f3e 0.542541420582 22401 of 0 -

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": 16177, "vin": [ { "gen": { "height": 16167 } } ], "vout": [ { "amount": 542541420582, "target": { "key": "2948bc3ead56caecdcd1f88e91ec0d45dacf056a36ffa1d20dfad07a1e001f3e" } } ], "extra": [ 1, 84, 203, 73, 116, 52, 140, 146, 69, 217, 108, 138, 49, 134, 183, 212, 75, 55, 245, 32, 80, 98, 217, 218, 5, 245, 3, 185, 219, 68, 210, 127, 219, 2, 17, 0, 0, 0, 7, 249, 82, 37, 165, 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: