Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f49674e37b13580bf2d9545ccd98ec63e457379f4d26aae0a4533992d6f25073

Tx prefix hash: 136972922d0149a7a858728b582e8a641e3beea87a312b4ccfeb5fc5f9b0b72a
Tx public key: c7d65010fcc16cc83854ee9cb7c745e502783b745ba7b77df200c7942ca8a106
Timestamp: 1698210630 Timestamp [UCT]: 2023-10-25 05:10:30 Age [y:d:h:m:s]: 01:174:01:17:04
Block: 877128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385400 RingCT/type: yes/0
Extra: 01c7d65010fcc16cc83854ee9cb7c745e502783b745ba7b77df200c7942ca8a10602110000000233af99f4000000000000000000

1 output(s) for total of 0.761571774000 dcy

stealth address amount amount idx
00: 09b976182d4ccdee4d5bd3582d7268d5fa7a036eba78969d742f238bd979ae99 0.761571774000 1332488 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": 877138, "vin": [ { "gen": { "height": 877128 } } ], "vout": [ { "amount": 761571774, "target": { "key": "09b976182d4ccdee4d5bd3582d7268d5fa7a036eba78969d742f238bd979ae99" } } ], "extra": [ 1, 199, 214, 80, 16, 252, 193, 108, 200, 56, 84, 238, 156, 183, 199, 69, 229, 2, 120, 59, 116, 91, 167, 183, 125, 242, 0, 199, 148, 44, 168, 161, 6, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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