Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90b5cd1a769f7dfa5408a56d85a55a00d1d70b699cfa510f8470a3426be4a88e

Tx prefix hash: 4b990431b41f898b19c0974f3c4f1f6687c1181fe7c0929b29f3c02dfacbbe31
Tx public key: ab81f43ec6ec09822c3790bb93765c429f4d9a7a365bade4fb61b757b59f9fa4
Timestamp: 1647952329 Timestamp [UTC]: 2022-03-22 12:32:09 Age [y:d:h:m:s]: 04:245:22:01:48
Block: 463955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1219539 RingCT/type: yes/0
Extra: 01ab81f43ec6ec09822c3790bb93765c429f4d9a7a365bade4fb61b757b59f9fa4021100000002cb8520c2000000000000000000

1 output(s) for total of 0.017812494631 xmr

stealth address amount amount idx tag
00: c7e2e18674d1399e922b60a43de0fe26ad205c171d1e53b2f96e8878fbd854f7 0.017812494631 881724 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": 463965, "vin": [ { "gen": { "height": 463955 } } ], "vout": [ { "amount": 17812494631, "target": { "key": "c7e2e18674d1399e922b60a43de0fe26ad205c171d1e53b2f96e8878fbd854f7" } } ], "extra": [ 1, 171, 129, 244, 62, 198, 236, 9, 130, 44, 55, 144, 187, 147, 118, 92, 66, 159, 77, 154, 122, 54, 91, 173, 228, 251, 97, 183, 87, 181, 159, 159, 164, 2, 17, 0, 0, 0, 2, 203, 133, 32, 194, 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: