Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad8a1605869adb2587cb819e668523c0f5dd401289ad192e14e7b608f67e6e3d

Tx prefix hash: f8899b04d90e2be896e67b490d1596241070579975d29bb7184045dd1845172d
Tx public key: e4cd027b85bb24e3cf985ddc84b267b68c3809671cb97b85ab91ccc9bcef0d5d
Timestamp: 1670538241 Timestamp [UCT]: 2022-12-08 22:24:01 Age [y:d:h:m:s]: 02:100:19:36:37
Block: 648386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593759 RingCT/type: yes/0
Extra: 01e4cd027b85bb24e3cf985ddc84b267b68c3809671cb97b85ab91ccc9bcef0d5d0211000000017e406890000000000000000000

1 output(s) for total of 4.361421027000 dcy

stealth address amount amount idx
00: 90d26c0da2ec1caf713df091d38d9a201b76ad10c381f5d0c72f5a65762333f5 4.361421027000 1088721 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": 648396, "vin": [ { "gen": { "height": 648386 } } ], "vout": [ { "amount": 4361421027, "target": { "key": "90d26c0da2ec1caf713df091d38d9a201b76ad10c381f5d0c72f5a65762333f5" } } ], "extra": [ 1, 228, 205, 2, 123, 133, 187, 36, 227, 207, 152, 93, 220, 132, 178, 103, 182, 140, 56, 9, 103, 28, 185, 123, 133, 171, 145, 204, 201, 188, 239, 13, 93, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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