Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6553aa9403de9b52b36adb882c782ba1fbbc10b0b75f5d4ea1c8a5d76d9caaf

Tx prefix hash: 928e0cef4b981c78556f512028164b5a0fb90fb43495601e07cca0069ac42721
Tx public key: 40fff1fd2a1c2e6a64b8951d56bc61948a5ceece1583f3fe78fdf51483bdedfd
Timestamp: 1621569958 Timestamp [UCT]: 2021-05-21 04:05:58 Age [y:d:h:m:s]: 04:168:08:46:54
Block: 264374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140418 RingCT/type: yes/0
Extra: 0140fff1fd2a1c2e6a64b8951d56bc61948a5ceece1583f3fe78fdf51483bdedfd02110000000f85d8f8f2000000000000000000

1 output(s) for total of 81.661947541000 dcy

stealth address amount amount idx
00: 8a8b48b4507fdd9c7154e9612e228f28c931e7c58996082e6e89afc8280d722f 81.661947541000 555924 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": 264384, "vin": [ { "gen": { "height": 264374 } } ], "vout": [ { "amount": 81661947541, "target": { "key": "8a8b48b4507fdd9c7154e9612e228f28c931e7c58996082e6e89afc8280d722f" } } ], "extra": [ 1, 64, 255, 241, 253, 42, 28, 46, 106, 100, 184, 149, 29, 86, 188, 97, 148, 138, 92, 238, 206, 21, 131, 243, 254, 120, 253, 245, 20, 131, 189, 237, 253, 2, 17, 0, 0, 0, 15, 133, 216, 248, 242, 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