Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 547f598ee1be11c48d7e91776665abe78e32bedd5c578e25e6203e3ea53eaaba

Tx prefix hash: 6d478e5d1019fc59110301604f0c72e928b44e196cce7d60e5ef0268d6068522
Tx public key: 2fca3fa22a3bf3c947a74ecd7324cf176461bbfd36e6ec11f3aec0d6ceaf9d0c
Timestamp: 1638538026 Timestamp [UTC]: 2021-12-03 13:27:06 Age [y:d:h:m:s]: 04:353:10:56:17
Block: 387540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1295496 RingCT/type: yes/0
Extra: 012fca3fa22a3bf3c947a74ecd7324cf176461bbfd36e6ec11f3aec0d6ceaf9d0c02110000002fd6e4826b000000000000000000

1 output(s) for total of 0.031909461428 xmr

stealth address amount amount idx tag
00: baf24fe5d2d4e8df10f953c0bcee562650bef255cc7b17e65ae6db82280b8e4b 0.031909461428 781619 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": 387550, "vin": [ { "gen": { "height": 387540 } } ], "vout": [ { "amount": 31909461428, "target": { "key": "baf24fe5d2d4e8df10f953c0bcee562650bef255cc7b17e65ae6db82280b8e4b" } } ], "extra": [ 1, 47, 202, 63, 162, 42, 59, 243, 201, 71, 167, 78, 205, 115, 36, 207, 23, 100, 97, 187, 253, 54, 230, 236, 17, 243, 174, 192, 214, 206, 175, 157, 12, 2, 17, 0, 0, 0, 47, 214, 228, 130, 107, 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: