Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d7f81272bb1fd824bd03c833e402a24ccce2028a0cd279fa970e2636d15e7b9

Tx prefix hash: dbb84cf9237624ad1d9228595e2b2b6a4cfd13b74779a5571ab3b1d7bd63a14c
Tx public key: 1cb8a94652c4d2ab67bf88b235a4c778c0f158e778185e78b01eab04ebb4fe27
Timestamp: 1725056903 Timestamp [UCT]: 2024-08-30 22:28:23 Age [y:d:h:m:s]: 00:256:13:57:45
Block: 1099469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183275 RingCT/type: yes/0
Extra: 011cb8a94652c4d2ab67bf88b235a4c778c0f158e778185e78b01eab04ebb4fe27021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0daf28cdad66c74073f2daf48b2c92a61c660adb6fc639bdafe7e2927e7ad0d0 0.600000000000 1575430 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": 1099479, "vin": [ { "gen": { "height": 1099469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0daf28cdad66c74073f2daf48b2c92a61c660adb6fc639bdafe7e2927e7ad0d0" } } ], "extra": [ 1, 28, 184, 169, 70, 82, 196, 210, 171, 103, 191, 136, 178, 53, 164, 199, 120, 192, 241, 88, 231, 120, 24, 94, 120, 176, 30, 171, 4, 235, 180, 254, 39, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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