Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feee48f326a763e7f176706d8b6ce431b11538bad73b8ed376e2bf7c42f48587

Tx prefix hash: 52636538fc45412812c61e5a8082a590e4f0caec1100be918fa313fd9937cd94
Tx public key: 520f7f2cbd6c0e89d5d239e2233b80fca073fa1e94adea86430dead9883f59cb
Timestamp: 1577526480 Timestamp [UCT]: 2019-12-28 09:48:00 Age [y:d:h:m:s]: 04:334:13:49:42
Block: 33341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128392 RingCT/type: yes/0
Extra: 01520f7f2cbd6c0e89d5d239e2233b80fca073fa1e94adea86430dead9883f59cb021100000003d81c26c0000000000000000000

1 output(s) for total of 475.913784363000 dcy

stealth address amount amount idx
00: 9c9c4be083d078444a85b4393af0b6625247c393af4c56f4a552c77235996c01 475.913784363000 55813 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": 33351, "vin": [ { "gen": { "height": 33341 } } ], "vout": [ { "amount": 475913784363, "target": { "key": "9c9c4be083d078444a85b4393af0b6625247c393af4c56f4a552c77235996c01" } } ], "extra": [ 1, 82, 15, 127, 44, 189, 108, 14, 137, 213, 210, 57, 226, 35, 59, 128, 252, 160, 115, 250, 30, 148, 173, 234, 134, 67, 13, 234, 217, 136, 63, 89, 203, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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