Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3491d5bb4cdb04de4a7c3bf9b57889dacf7cf0bc8e6f263d9ff3c7e40cc3bcf6

Tx prefix hash: 21f57c33d64193aef81ee336af5a8838a3df460c05926d653c5a66b2c4335465
Tx public key: 9a9fa3708c2e898af892052d091c8f12db523e78e142020d8d1f2393319c2795
Timestamp: 1740407689 Timestamp [UTC]: 2025-02-24 14:34:49 Age [y:d:h:m:s]: 01:263:16:08:53
Block: 1226276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452433 RingCT/type: yes/0
Extra: 019a9fa3708c2e898af892052d091c8f12db523e78e142020d8d1f2393319c279502110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aa70040db7d06618053842c2d4f786f4621f96bb58c2e2ca1d12f243bb605f2f 0.000600000000 1713147 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": 1226286, "vin": [ { "gen": { "height": 1226276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa70040db7d06618053842c2d4f786f4621f96bb58c2e2ca1d12f243bb605f2f" } } ], "extra": [ 1, 154, 159, 163, 112, 140, 46, 137, 138, 248, 146, 5, 45, 9, 28, 143, 18, 219, 82, 62, 120, 225, 66, 2, 13, 141, 31, 35, 147, 49, 156, 39, 149, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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: