Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30639587cb9b0aaef5774cfda13ba9a3963b189103fe996d54c481811fab9cb2

Tx prefix hash: b39f0874146a2f12b0bcbe181a6ad274fd2a5d1cbb5fe8554e708b5bd74813f5
Tx public key: c1e1bbd43a721f64911a3f58d04b8b5313805beba67ef285445ae8e0170b8d5d
Timestamp: 1626713271 Timestamp [UTC]: 2021-07-19 16:47:51 Age [y:d:h:m:s]: 05:125:17:11:31
Block: 297045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1386290 RingCT/type: yes/0
Extra: 01c1e1bbd43a721f64911a3f58d04b8b5313805beba67ef285445ae8e0170b8d5d0211000000256367b7e9000000000000000000

1 output(s) for total of 0.063645411765 xmr

stealth address amount amount idx tag
00: 7a81472d6d6b5b44f7ca0fb46d6772ea0f53af3353467dc307a9ba8c7a814d90 0.063645411765 621769 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": 297055, "vin": [ { "gen": { "height": 297045 } } ], "vout": [ { "amount": 63645411765, "target": { "key": "7a81472d6d6b5b44f7ca0fb46d6772ea0f53af3353467dc307a9ba8c7a814d90" } } ], "extra": [ 1, 193, 225, 187, 212, 58, 114, 31, 100, 145, 26, 63, 88, 208, 75, 139, 83, 19, 128, 91, 235, 166, 126, 242, 133, 68, 90, 232, 224, 23, 11, 141, 93, 2, 17, 0, 0, 0, 37, 99, 103, 183, 233, 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: