Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd266b3b6350154ff5bf2599947464ef1d33a45ee5d77deb3e12c0bef9d8f3a7

Tx prefix hash: 4e1ff16fdd1f913df70cedfc21503d9bb3b816fa064e5ce078f281f08a36f5a4
Tx public key: c720bacc1d8c0df72c5e8dfb280458fb67361cf292228573cb06a7e059220897
Timestamp: 1653951730 Timestamp [UTC]: 2022-05-30 23:02:10 Age [y:d:h:m:s]: 04:176:03:25:38
Block: 512330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1171164 RingCT/type: yes/0
Extra: 01c720bacc1d8c0df72c5e8dfb280458fb67361cf292228573cb06a7e0592208970211000000015eb576c5000000000000000000

1 output(s) for total of 0.012315107839 xmr

stealth address amount amount idx tag
00: 16a2a9f4bf92e3c8f4019dc887cb8af1bb0ce44b6b7537151edfd0616db06f31 0.012315107839 938947 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": 512340, "vin": [ { "gen": { "height": 512330 } } ], "vout": [ { "amount": 12315107839, "target": { "key": "16a2a9f4bf92e3c8f4019dc887cb8af1bb0ce44b6b7537151edfd0616db06f31" } } ], "extra": [ 1, 199, 32, 186, 204, 29, 140, 13, 247, 44, 94, 141, 251, 40, 4, 88, 251, 103, 54, 28, 242, 146, 34, 133, 115, 203, 6, 167, 224, 89, 34, 8, 151, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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: