Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feedcbbce3e923afd05f1b9da8ae5f865dd194736d98e11a48af2da1a5b92f66

Tx prefix hash: 63744a2c2cf6deafbc542b46563661fb4010e065d958afee8a1d06f41cdfcb68
Tx public key: d2ee433f14e8ce984caa9115d9e0aedefd90e230d4747af9a82e6d8f354acc73
Timestamp: 1582644169 Timestamp [UCT]: 2020-02-25 15:22:49 Age [y:d:h:m:s]: 04:305:20:33:47
Block: 72353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111226 RingCT/type: yes/0
Extra: 01d2ee433f14e8ce984caa9115d9e0aedefd90e230d4747af9a82e6d8f354acc73021100000003026b59f3000000000000000000

1 output(s) for total of 353.398967294000 dcy

stealth address amount amount idx
00: 78eef97e1d1fd305f4d782f7f4f737c3de6d4f49c762b90f1d064c4f25db0a0c 353.398967294000 133570 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": 72363, "vin": [ { "gen": { "height": 72353 } } ], "vout": [ { "amount": 353398967294, "target": { "key": "78eef97e1d1fd305f4d782f7f4f737c3de6d4f49c762b90f1d064c4f25db0a0c" } } ], "extra": [ 1, 210, 238, 67, 63, 20, 232, 206, 152, 76, 170, 145, 21, 217, 224, 174, 222, 253, 144, 226, 48, 212, 116, 122, 249, 168, 46, 109, 143, 53, 74, 204, 115, 2, 17, 0, 0, 0, 3, 2, 107, 89, 243, 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