Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7c069e6843947484115478bc510b50110dedfcfe3e37de168f3ad74bfff06eb

Tx prefix hash: 20d74b4b77e7602890f0e841e94f32ef0c11f6f79fcae5e1886d1ed5c2d9c7d7
Tx public key: 2934e919ea7ee3632734b22181941dab930d7a8acc047462e859e35871a0995e
Timestamp: 1581083821 Timestamp [UCT]: 2020-02-07 13:57:01 Age [y:d:h:m:s]: 04:152:06:10:35
Block: 60233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1000491 RingCT/type: yes/0
Extra: 012934e919ea7ee3632734b22181941dab930d7a8acc047462e859e35871a0995e0211000000048a2ee0d9000000000000000000

1 output(s) for total of 387.642505088000 dcy

stealth address amount amount idx
00: 3bf051516555fbd01ea58a21818bd3c1933f2c1b9d25a5e3a4d5e1af75bb04af 387.642505088000 111091 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": 60243, "vin": [ { "gen": { "height": 60233 } } ], "vout": [ { "amount": 387642505088, "target": { "key": "3bf051516555fbd01ea58a21818bd3c1933f2c1b9d25a5e3a4d5e1af75bb04af" } } ], "extra": [ 1, 41, 52, 233, 25, 234, 126, 227, 99, 39, 52, 178, 33, 129, 148, 29, 171, 147, 13, 122, 138, 204, 4, 116, 98, 232, 89, 227, 88, 113, 160, 153, 94, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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