Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ca0c22af5e6c6992d32cde9cb300bfde49c7dfd4ce4c9a1d88aea25f95377fc

Tx prefix hash: 4eaaf6bbc858cbc07453963d3d2a1939d4cafa93257f2bdd7c86999624f311ea
Tx public key: 7992fdb0b454045b71f72e34477df079f922a94ce2361f42a7e8984530d8bf15
Timestamp: 1731310397 Timestamp [UCT]: 2024-11-11 07:33:17 Age [y:d:h:m:s]: 00:221:17:55:36
Block: 1151237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158187 RingCT/type: yes/0
Extra: 017992fdb0b454045b71f72e34477df079f922a94ce2361f42a7e8984530d8bf150211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a94bf3069fe7ef587e1ade31be57e55ecc0d6bff141d8de955d3568ab260dc5 0.600000000000 1636730 of 15

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": 1151247, "vin": [ { "gen": { "height": 1151237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a94bf3069fe7ef587e1ade31be57e55ecc0d6bff141d8de955d3568ab260dc5" } } ], "extra": [ 1, 121, 146, 253, 176, 180, 84, 4, 91, 113, 247, 46, 52, 71, 125, 240, 121, 249, 34, 169, 76, 226, 54, 31, 66, 167, 232, 152, 69, 48, 216, 191, 21, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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