Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 574ce39f518fd147eec5ea1ae031819234652b679ea694cb808535a963960f6b

Tx prefix hash: 9aa7f2dc4661d67081174ecd0ae9ce40d7ffda45f1cc48f094770ac86922c3e6
Tx public key: 563ef6e3cea651f703aef5a1c2b7379001db5b25b2d56b583b9e3521993a1b05
Timestamp: 1581978234 Timestamp [UCT]: 2020-02-17 22:23:54 Age [y:d:h:m:s]: 04:316:02:36:11
Block: 67053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118323 RingCT/type: yes/0
Extra: 01563ef6e3cea651f703aef5a1c2b7379001db5b25b2d56b583b9e3521993a1b0502110000002b4ac5aa02000000000000000000

1 output(s) for total of 367.981837726000 dcy

stealth address amount amount idx
00: 1d6ecaed820a17a13cb7034b096bfaa80e5cc270f51fc5a84a8c30153f6bde86 367.981837726000 123513 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": 67063, "vin": [ { "gen": { "height": 67053 } } ], "vout": [ { "amount": 367981837726, "target": { "key": "1d6ecaed820a17a13cb7034b096bfaa80e5cc270f51fc5a84a8c30153f6bde86" } } ], "extra": [ 1, 86, 62, 246, 227, 206, 166, 81, 247, 3, 174, 245, 161, 194, 183, 55, 144, 1, 219, 91, 37, 178, 213, 107, 88, 59, 158, 53, 33, 153, 58, 27, 5, 2, 17, 0, 0, 0, 43, 74, 197, 170, 2, 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