Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d26f59037c53cdea881745ff5a1eb336f15f31fc9de171e51c9c75f8787ed133

Tx prefix hash: cfcf53894d22637ae64ed4dd07e0a3b6037addd668a2028f4031a64fc6ff3587
Tx public key: ddbc8a841aa5f241540370cfb960abddb66913d63ee62ca161b6649424c32b22
Timestamp: 1699714116 Timestamp [UCT]: 2023-11-11 14:48:36 Age [y:d:h:m:s]: 01:137:18:46:07
Block: 889377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359648 RingCT/type: yes/0
Extra: 01ddbc8a841aa5f241540370cfb960abddb66913d63ee62ca161b6649424c32b2202110000000333af99f4000000000000000000

1 output(s) for total of 0.693625099000 dcy

stealth address amount amount idx
00: e660e8a2b0cfb4e40513ecdf0bd6978f5a4e5d486fd8c9fd87b4b2971cf0a67c 0.693625099000 1345374 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": 889387, "vin": [ { "gen": { "height": 889377 } } ], "vout": [ { "amount": 693625099, "target": { "key": "e660e8a2b0cfb4e40513ecdf0bd6978f5a4e5d486fd8c9fd87b4b2971cf0a67c" } } ], "extra": [ 1, 221, 188, 138, 132, 26, 165, 242, 65, 84, 3, 112, 207, 185, 96, 171, 221, 182, 105, 19, 214, 62, 230, 44, 161, 97, 182, 100, 148, 36, 195, 43, 34, 2, 17, 0, 0, 0, 3, 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