Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fc3d924360b443bbe96c0a88632bc43b443543e88a8f631b35c3773c6088ed6

Tx prefix hash: 2b80dcf8518645bd24f9f8b6d97226a04482ca6e5117cb2faa088d1bf3b76410
Tx public key: dcdc33b6fce96e6453a0cf23d59e7a691514179486e93d5828326d2f46c9aff3
Timestamp: 1631462520 Timestamp [UCT]: 2021-09-12 16:02:00 Age [y:d:h:m:s]: 03:074:20:22:23
Block: 332400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 829002 RingCT/type: yes/0
Extra: 01dcdc33b6fce96e6453a0cf23d59e7a691514179486e93d5828326d2f46c9aff302110000000136fe6557000000000000000000

1 output(s) for total of 48.598320097000 dcy

stealth address amount amount idx
00: 9c84598890270c71ed8ef4ffe27fdcb59f2bba5ea9d2c9d7eebe13717c62067a 48.598320097000 686423 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": 332410, "vin": [ { "gen": { "height": 332400 } } ], "vout": [ { "amount": 48598320097, "target": { "key": "9c84598890270c71ed8ef4ffe27fdcb59f2bba5ea9d2c9d7eebe13717c62067a" } } ], "extra": [ 1, 220, 220, 51, 182, 252, 233, 110, 100, 83, 160, 207, 35, 213, 158, 122, 105, 21, 20, 23, 148, 134, 233, 61, 88, 40, 50, 109, 47, 70, 201, 175, 243, 2, 17, 0, 0, 0, 1, 54, 254, 101, 87, 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