Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fd1aad74954f973a911ccfa08f187ca9387ab0d0911de71efcb39ac9e5bec2d

Tx prefix hash: 1fd51174fbb0412f7557b214b3cef1459eba881fc032323c31d788a6618bd912
Tx public key: 466ae7b1f4aee67f7be15db13cfbd6a6214f70d27dfcba6a5a548b89983bfe38
Timestamp: 1632157065 Timestamp [UCT]: 2021-09-20 16:57:45 Age [y:d:h:m:s]: 04:045:11:09:31
Block: 337656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1066883 RingCT/type: yes/0
Extra: 01466ae7b1f4aee67f7be15db13cfbd6a6214f70d27dfcba6a5a548b89983bfe3802110000002736fe6557000000000000000000

1 output(s) for total of 46.688071994000 dcy

stealth address amount amount idx
00: fde5a422e0c09ae068592e0faae4ea42558f13eca9a2a4e45649c437d8381d82 46.688071994000 695197 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": 337666, "vin": [ { "gen": { "height": 337656 } } ], "vout": [ { "amount": 46688071994, "target": { "key": "fde5a422e0c09ae068592e0faae4ea42558f13eca9a2a4e45649c437d8381d82" } } ], "extra": [ 1, 70, 106, 231, 177, 244, 174, 230, 127, 123, 225, 93, 177, 60, 251, 214, 166, 33, 79, 112, 210, 125, 252, 186, 106, 90, 84, 139, 137, 152, 59, 254, 56, 2, 17, 0, 0, 0, 39, 54, 254, 101, 87, 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