Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21b4bdf4a95755deaf6d138aff6a9631720c293ecb4df1e5085e03ac23759e60

Tx prefix hash: 2023835f68668719a1da72b684f203dbca37027d2ed0bbc6a5c4c7ce94aa5136
Tx public key: 741bacd7fd647eb315001dafcf3a61a2cf4494aa36de49c9d814d030362ead73
Timestamp: 1673051218 Timestamp [UCT]: 2023-01-07 00:26:58 Age [y:d:h:m:s]: 01:330:08:23:46
Block: 669181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497127 RingCT/type: yes/0
Extra: 01741bacd7fd647eb315001dafcf3a61a2cf4494aa36de49c9d814d030362ead73021100000001faf35c9c000000000000000000

1 output(s) for total of 3.721564199000 dcy

stealth address amount amount idx
00: 8195123bf0a7c258f7eddfcfd82d0d9255d9d5e23d0e6aae85816048db631745 3.721564199000 1110484 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 dinasty-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": 669191, "vin": [ { "gen": { "height": 669181 } } ], "vout": [ { "amount": 3721564199, "target": { "key": "8195123bf0a7c258f7eddfcfd82d0d9255d9d5e23d0e6aae85816048db631745" } } ], "extra": [ 1, 116, 27, 172, 215, 253, 100, 126, 179, 21, 0, 29, 175, 207, 58, 97, 162, 207, 68, 148, 170, 54, 222, 73, 201, 216, 20, 208, 48, 54, 46, 173, 115, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8