Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3fc2be7aa40e454d2bbd1e4b3611641f603c4f46ac8599b75e95c827e3b24e6

Tx prefix hash: 6beb94fd045aed96504f1e4935b5f6a00b3ef081a49f3e7ae54d1abb4683c852
Tx public key: b7bbd708b528dec9156f67256314a35c3c75a8d07b2c62dd8d719ccc5bc37838
Timestamp: 1625445039 Timestamp [UCT]: 2021-07-05 00:30:39 Age [y:d:h:m:s]: 04:208:08:40:04
Block: 288361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1177005 RingCT/type: yes/0
Extra: 01b7bbd708b528dec9156f67256314a35c3c75a8d07b2c62dd8d719ccc5bc37838021100000023694a138f000000000000000000

1 output(s) for total of 68.004994532000 dcy

stealth address amount amount idx
00: 016fa5994d6f381ed1d13dd0b9441913b95bd6e4d3675c17a8ae80649e2280d3 68.004994532000 604186 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": 288371, "vin": [ { "gen": { "height": 288361 } } ], "vout": [ { "amount": 68004994532, "target": { "key": "016fa5994d6f381ed1d13dd0b9441913b95bd6e4d3675c17a8ae80649e2280d3" } } ], "extra": [ 1, 183, 187, 215, 8, 181, 40, 222, 201, 21, 111, 103, 37, 99, 20, 163, 92, 60, 117, 168, 208, 123, 44, 98, 221, 141, 113, 156, 204, 91, 195, 120, 56, 2, 17, 0, 0, 0, 35, 105, 74, 19, 143, 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