Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20bb2a4f0e195a92d22feaa886962a85bc0747091b7122a8480452697a6e174d

Tx prefix hash: 61c354004f6160ba602928abbc7f4cfc9c0eb3620acf0e730bd4dfcaa8a12e6a
Tx public key: 7e37fd5ee660f946f77f0285424e992e3299d7790c6984f8c643e79d16753336
Timestamp: 1713500835 Timestamp [UCT]: 2024-04-19 04:27:15 Age [y:d:h:m:s]: 00:332:06:46:04
Block: 1003671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237563 RingCT/type: yes/0
Extra: 017e37fd5ee660f946f77f0285424e992e3299d7790c6984f8c643e79d16753336021100000003e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60d559990b920782c82845e5942f4d8639ca7777edaf60fd0c26f6dff4ff336f 0.600000000000 1464213 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": 1003681, "vin": [ { "gen": { "height": 1003671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60d559990b920782c82845e5942f4d8639ca7777edaf60fd0c26f6dff4ff336f" } } ], "extra": [ 1, 126, 55, 253, 94, 230, 96, 249, 70, 247, 127, 2, 133, 66, 78, 153, 46, 50, 153, 215, 121, 12, 105, 132, 248, 198, 67, 231, 157, 22, 117, 51, 54, 2, 17, 0, 0, 0, 3, 228, 187, 107, 131, 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