Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 637c288bc225ceb91c992ae0f9105ee9f4297d7fb2f96534146ffb5c1332f6ff

Tx prefix hash: d1a6ac5b0a5e55f5fb13f31e65649a35ac4aa73788554a25a6f55b9f89b4ec81
Tx public key: d933b19a84e2817de23385569fdf085213d1262d1c4791b700325efdcb92064a
Timestamp: 1702137962 Timestamp [UCT]: 2023-12-09 16:06:02 Age [y:d:h:m:s]: 01:148:00:22:03
Block: 909475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366951 RingCT/type: yes/0
Extra: 01d933b19a84e2817de23385569fdf085213d1262d1c4791b700325efdcb92064a0211000000024b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 420bb7a3952c8edcf2f52f63fabdb3519cfd3f3af2609e45c43feda73b780606 0.600000000000 1366564 of 15

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": 909485, "vin": [ { "gen": { "height": 909475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "420bb7a3952c8edcf2f52f63fabdb3519cfd3f3af2609e45c43feda73b780606" } } ], "extra": [ 1, 217, 51, 177, 154, 132, 226, 129, 125, 226, 51, 133, 86, 159, 223, 8, 82, 19, 209, 38, 45, 28, 71, 145, 183, 0, 50, 94, 253, 203, 146, 6, 74, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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