Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c0263d91742c1a031642126c826f2e379876e45142e503136319b38c6f10525

Tx prefix hash: e0ed38130ac29f11bc951ef581a263d269d5070009d4d8bd30b413b9c90a880e
Tx public key: 1fd6aa12eac64a13c12ba736a63d86961d52d235a9ce85adc3d489b7020aec99
Timestamp: 1700788928 Timestamp [UCT]: 2023-11-24 01:22:08 Age [y:d:h:m:s]: 01:137:07:03:05
Block: 898283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359297 RingCT/type: yes/0
Extra: 011fd6aa12eac64a13c12ba736a63d86961d52d235a9ce85adc3d489b7020aec990211000000014b8f5122000000000000000000

1 output(s) for total of 0.648060441000 dcy

stealth address amount amount idx
00: 63ab82080643a870f229e2b644fb7d3e54949ca3246e6beae5e07f10b72ac7fa 0.648060441000 1354696 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": 898293, "vin": [ { "gen": { "height": 898283 } } ], "vout": [ { "amount": 648060441, "target": { "key": "63ab82080643a870f229e2b644fb7d3e54949ca3246e6beae5e07f10b72ac7fa" } } ], "extra": [ 1, 31, 214, 170, 18, 234, 198, 74, 19, 193, 43, 167, 54, 166, 61, 134, 150, 29, 82, 210, 53, 169, 206, 133, 173, 195, 212, 137, 183, 2, 10, 236, 153, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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