Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 916418953bb0e3fca2c19da5e7ed7fc4d66828ff16faf7d94e554588bcfea37c

Tx prefix hash: e1d2f008cbaccf07abbdf6529a32ecf3cb89850ba39c52e72f37be23c0dfdbd0
Tx public key: 3aafc990b5ff8f2d722e64d8726aec9a3d425fe13591fc97c595c75895f2c8c0
Timestamp: 1724881806 Timestamp [UCT]: 2024-08-28 21:50:06 Age [y:d:h:m:s]: 00:220:01:16:41
Block: 1098021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157132 RingCT/type: yes/0
Extra: 013aafc990b5ff8f2d722e64d8726aec9a3d425fe13591fc97c595c75895f2c8c0021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 682de1983776e80adc0109f56a8f7df1c4ff98bcefc4606208abb2c72068c1c8 0.600000000000 1573596 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": 1098031, "vin": [ { "gen": { "height": 1098021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "682de1983776e80adc0109f56a8f7df1c4ff98bcefc4606208abb2c72068c1c8" } } ], "extra": [ 1, 58, 175, 201, 144, 181, 255, 143, 45, 114, 46, 100, 216, 114, 106, 236, 154, 61, 66, 95, 225, 53, 145, 252, 151, 197, 149, 199, 88, 149, 242, 200, 192, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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