Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0bdf8f9c7e56470183513f7eeb61dafb21d78e17d3cc474fbaa85b23230298e

Tx prefix hash: 8ecb4bdceeb9af4d7035e250e5fbd092a4bc493d5d6d71e185ceef34810bd241
Tx public key: 3ac278b29a2c997ee20ea3031c7bcbb6a001516a26795a654bfcd8c589338862
Timestamp: 1582906355 Timestamp [UCT]: 2020-02-28 16:12:35 Age [y:d:h:m:s]: 04:301:09:02:18
Block: 73516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109028 RingCT/type: yes/0
Extra: 013ac278b29a2c997ee20ea3031c7bcbb6a001516a26795a654bfcd8c58933886202110000000b4943cd9f000000000000000000

1 output(s) for total of 350.277122620000 dcy

stealth address amount amount idx
00: ef75db65c7a26964249ee0ed0f509f7476b271e22e0a4d291daf41fef8b3ed15 350.277122620000 135659 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": 73526, "vin": [ { "gen": { "height": 73516 } } ], "vout": [ { "amount": 350277122620, "target": { "key": "ef75db65c7a26964249ee0ed0f509f7476b271e22e0a4d291daf41fef8b3ed15" } } ], "extra": [ 1, 58, 194, 120, 178, 154, 44, 153, 126, 226, 14, 163, 3, 28, 123, 203, 182, 160, 1, 81, 106, 38, 121, 90, 101, 75, 252, 216, 197, 137, 51, 136, 98, 2, 17, 0, 0, 0, 11, 73, 67, 205, 159, 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