Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf3261c3a45ab1ec95d1f896a45fec0587392d40a07741399b9ea9ef289c13f4

Tx prefix hash: c3da99cfb08b4d8a9215cb0ebf99fa21c17ffb34eb9a579db274d7a5fd233e8a
Tx public key: 994ad3e557b44003a2c37b0efa507e2497c16696affa07d210a708c3057d3878
Timestamp: 1634969997 Timestamp [UCT]: 2021-10-23 06:19:57 Age [y:d:h:m:s]: 03:107:17:03:35
Block: 358633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 855056 RingCT/type: yes/0
Extra: 01994ad3e557b44003a2c37b0efa507e2497c16696affa07d210a708c3057d387802110000000106faf294000000000000000000

1 output(s) for total of 39.783263501000 dcy

stealth address amount amount idx
00: c2121daf2c1ed5df75bf9558e9b56dbdea27c92b4a90706d43a3d7e152947714 39.783263501000 730656 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": 358643, "vin": [ { "gen": { "height": 358633 } } ], "vout": [ { "amount": 39783263501, "target": { "key": "c2121daf2c1ed5df75bf9558e9b56dbdea27c92b4a90706d43a3d7e152947714" } } ], "extra": [ 1, 153, 74, 211, 229, 87, 180, 64, 3, 162, 195, 123, 14, 250, 80, 126, 36, 151, 193, 102, 150, 175, 250, 7, 210, 16, 167, 8, 195, 5, 125, 56, 120, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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