Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63c01d038ec18e5a2b8bf237fdabbb707e6811faad423ccb9e2300a06cb08157

Tx prefix hash: ba2ec2105500558620f5d34fd08eab15790fa4540b664e6d83d45f6a4dd524e7
Tx public key: 23b2c23fe1a3a55b146e78664d8d5ee659175297668a35b04c22e8cbffae1f88
Timestamp: 1772461030 Timestamp [UTC]: 2026-03-02 14:17:10 Age [y:d:h:m:s]: 00:263:16:45:41
Block: 1489116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194124 RingCT/type: yes/0
Extra: 0123b2c23fe1a3a55b146e78664d8d5ee659175297668a35b04c22e8cbffae1f88021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 69ede3b519f3096ccf8ae5c5acf05b2dc6cdad868495ce99b72257b23831692b 0.000600000000 1978604 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": 1489126, "vin": [ { "gen": { "height": 1489116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69ede3b519f3096ccf8ae5c5acf05b2dc6cdad868495ce99b72257b23831692b" } } ], "extra": [ 1, 35, 178, 194, 63, 225, 163, 165, 91, 20, 110, 120, 102, 77, 141, 94, 230, 89, 23, 82, 151, 102, 138, 53, 176, 76, 34, 232, 203, 255, 174, 31, 136, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: